An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hello, Our app FORGED (Apple ID 6818932334) was rejected on Oct 23 under Guideline 5.1.1(iv). The only issue was the button on our HealthKit pre-permission screen, which said “Connect Apple Health”. We changed it to “Continue” and resubmitted build 85 the same day. Since then it has been in “Waiting for Review” for 6 days with no change. We have already: Sent an expedite request Contacted App Review through the Contact Us form Followed up on that message We haven’t received any response yet. Is this normal right now, or could something be blocking the submission? Is there anything else we should do on our side? Thank you for any help.

Hi all, I'm wondering if anyone else is seeing this right now, or has been through it before. I resubmitted my iOS app (version 1.0, with one In-App Purchase in the same submission) on October 16 after answering a Guideline 2.1 information request. I requested an expedited review the same day and it was accepted. It has now been 13 days, and both the app and the In-App Purchase are still in "Waiting for Review". Nothing in App Store Connect has changed since October 16, and there are no new messages from App Review. I've contacted Developer Support by email several times and once by phone. Their latest reply only confirmed that the expedited review was accepted and that the review "should begin shortly". For those who had a similar wait: How long did it take before the review actually started? Did anything help, such as contacting a different support topic, or cancelling and resubmitting? Or did it just start on its own eventually? I'd rather not cancel and resubmit unless that's known to help. Apple ID of the app, in case it's useful: 6809826557 Thanks.

Our app, Nori (Apple ID 6823844486), has been in the "Waiting for Review" status since October 26, 2026 (version 1.0.1, build 11), with no change for more than 3 days. This build was resubmitted after addressing the feedback from our previous reviews: • Guideline 5.1.1(iv): the camera and notification pre-permission screens now use a neutral "Continue" button. • Guideline 5.6: we removed all code that was included in the binary but not visible to users. Our web version already has more than 1,000 users, and we are preparing to add a subscription after this version is approved. Right now everything is on hold because of this review. We are also entering an app contest whose deadline is approaching, and the app still shows "Waiting for Review." We have already submitted an expedited review request and also contacted Apple by email, but we have not received a reply yet. Could you please let us know: • Is there a specific reason for the extended hold? • Is any action required from our side (for example, information, agreements, or account settings)? • When can we expect the review to proceed? Thank you very much for your time and assistance.

I'm genuinely at a loss with Apple's App Review process. Our backend records show that across BOTH reviews, Apple's reviewers did not complete a SINGLE use of our app's core functionality. Not once. ZERO completed generations. For the latest review, our logs confirm Apple successfully logged in, but recorded ZERO generation requests and ZERO credits consumed. This isn't some minor feature. It's the entire foundation of our app. Our app fundamentally changes and becomes personalised as it's used. Without completing that process, you're essentially judging an incomplete product. Submission ID: 6a126514-9bb6-4d91-923c-bf29aacb1b68 Here's why this is so frustrating. We spent months deliberately building an app that offers functionality and a user experience fundamentally different from existing competitors. This wasn't another copycat app - avoiding that was central to its design from day one. We explained these differences extensively in our App Review notes. Yet Apple has rejected us TWICE under Guideline 4.3(b) — Design Spam. We even provided a narrated walkthrough demonstrating exactly what makes our app unique. Our video analytics show ZERO views. So we're being rejected for supposedly lacking originality, despite neither review producing a completed use of our main feature and no recorded views of our demonstration. After both rejections, we've received nothing but generic responses telling us to improve the app, without identifying a single specific problem. How are independent developers supposed to fix something when Apple won't explain what's wrong? We've now filed a formal appeal, which could take a month, with no visible queue position, progress updates or estimated timeframe. Meanwhile, we've already missed multiple planned marketing opportunities, and waiting could mean missing even more. We're not asking for guaranteed approval. We're asking for a fair review of what we've actually built. Has anyone else experienced this? What would you do? Wait for the appeal, hoping the App Review Board properly evaluates the app, even if it takes another month and we miss more deadlines? Withdraw the appeal and resubmit, hoping for a different reviewer, but risking another rejection without proper testing and further warnings against our developer account? I'd genuinely appreciate advice from anyone who's experienced something similar, especially those who've successfully appealed a 4.3(b) rejection. At this point, I genuinely don't know whether this is a reviewer misunderstanding, an automated rejection process, or something else entirely. But how can Apple determine that an app lacks originality when its defining functionality hasn't even been tested?

Hi everyone, My first app, Sort Rush: Package Factory (Apple ID: 6823296215), has been in "Waiting for Review" since October 17, 2026, and during this time I've made several attempts to move it forward: I replied to the "Guideline 2.1 - Information Needed - New App Submission" message on the same day, with a screen recording from a physical iPhone and all the requested information I submitted an expedited review request I used the Contact Us form to ask about the status (Case ID: 103005195582) Unfortunately, the status hasn't changed. I haven't cancelled or resubmitted the build, so I don't lose my place in the queue. The app is a simple offline puzzle game, rated 4+: no login, no user-generated content, no in-app purchases, only optional rewarded ads. I understand that new developer accounts need additional verification, but I'm not sure if anything else is needed from my side. I would really appreciate any help or suggestions on how to move the review forward. Thank you!

Hi everyone, After my app was rejected, repeated contact attempts and an appeal have not led to any meaningful guidance. What should I do next? Apple ID: 6807882674 Review timeline (all dates are in 2026): September 7: First submitted the app for App Store review. September 16: The app was rejected. I then sent three messages through Contact Us and received no reply to any of them. I subsequently submitted an appeal, which also received no response. During this period: I continued developing the app, updating the review information and resubmitting. Multiple TestFlight external beta builds were also rejected. When I contacted Apple about those rejections, the replies were generic process information with no specific advice on what to change. October 20 (UTC): Resubmitted the app for App Store review. As of October 27, it is still Waiting for Review, with no further update. It has been 50 days since my first submission, including rejection, an appeal and resubmissions. I understand that reviews take time. However, the replies I have received feel mechanical and unhelpful: they repeat general process information without addressing my specific questions or explaining what needs to change. I still do not know how to move forward. Has anyone experienced a similar situation? How can I obtain case-specific guidance? If an Apple staff member sees this, could you help check my case or advise on the next step? I can provide the relevant case numbers through the support channel. Thank you for your help. I will update this thread daily until there is substantive progress with the review.

Hello, Our first app, "Pizza Virus - Food Delivery" (Apple ID 6612290745), has been in "Waiting for Review" since October 13, 2026. Submission ID: ebbda6e3-893f-42b5-8398-0d7ee377695a Version 2.1.0, build 2.1.2 (3) This is a resubmission that fixes the launch crash App Review reported on October 6 (Guideline 2.1(a)). We added a UIApplicationSceneManifest and a SceneDelegate. We later found that the updated Program License Agreement (issued October 14) and our Free Apps Agreement were only accepted on October 23, which may have held the submission. Both are now active, and the Digital Services Act declaration is completed. We requested an expedited review and opened support case 103008067614, but have not received a response. Could App Review please confirm whether the submission is now in the review queue, or whether anything else is needed from us? Thank you.

Hi everyone, I submitted my iOS app (Hatırlatıcım) for review on October 13, and it's still showing "Waiting for Review" today, October 26. It's been almost two weeks now, and the status hasn't changed at all. I haven't received any emails or requests for additional information from Apple either. I contacted Developer Support on October 19, but haven't heard back from them yet. I've seen a few other developers mentioning similar delays recently, so I'm wondering if this is a general issue with App Store reviews right now. Has anyone who submitted an app around October 13–14 had theirs reviewed yet? I'm also not sure if I should just keep waiting or if there's anything else I can do at this point. Thanks!

Hello, My new app, feenixOS – all in one (Apple ID 6805282368), version 1.0 (build 125), has been in “Waiting for Review” since October 20, 2026. Submission ID: cd0e6349-4f24-4eb7-bdae-9a0a9f5a5989 Timeline: Oct 20, 10:28 AM: an automated message said the submission could not be reviewed because the age rating indicated simulated gambling (I’m an individual developer). The app has no simulated gambling. I corrected the age rating the same morning (it now shows 12+, no gambling) and resubmitted at 11:30 AM. Since then it has stayed in Waiting for Review with no messages. What I’ve done: called Developer Support twice (they noted it was blocking my business) and submitted an expedited review request on Oct 28. There’s no reply option in App Store Connect while it’s waiting. Could someone from App Review confirm the submission is in the queue normally, and that nothing is still holding it (for example, a hold left over from the automated rating check)? I’d rather not withdraw and resubmit and lose my place. Thank you for any help.

Our iOS app has been sitting in "In Review" for four weeks and we have not been able to get a status update through any channel, so I'm posting here in case someone from App Review can take a look. App: Epocra, iOS, version 1.0, build 268 Apple ID: 6813697639 Status: In Review since September 24, as Developer Support confirmed on October 1 Timeline Sept 22: build 267 rejected under 2.1(a), a launch crash on iPad Air running iPadOS 27. Fixed the same day and resubmitted as build 268. Sept 22: a reviewer signed in to the demo account that evening. No activity since. Sept 28: opened a status request through Contact Us, case 102979044954. On Oct 1 Developer Support replied that the review was "outside of our normal timeframe" and that the review team had been notified. Nothing since. Oct 5: second status request, case 102986888342. Acknowledgement only. Oct 9: replied in the App Review message thread for the submission citing both cases. No response. We have not changed anything on the submission while it is in review so we don't reset the queue. The app is a business phone app (CallKit and PushKit VoIP with server-side call recording and a consent screen on first launch). The review notes include a demo account, a walkthrough video, and a phone number the reviewer can call to test inbound calls. Is there anything else we should be doing to get this looked at, or can someone from App Review check on it? Happy to provide anything that would help.

I previously responded to thread 840483, but Apple Support staff have not responded. I've also responded in App Review and created a support email, but the response times have been inadequate, and in the email thread it seems that the responding agent(s) did not read or understand the context of the issue, so I'll make this post in the hope that someone from Apple Support can assist. Guideline 2.1(b) rejection, with no way to submit the in-app purchase and the version together. I’m hitting the same deadlock described in thread link text, and I’ve added my case because it looks systemic, not a one-off setup error. My situation New app, iOS 1.0. One non-consumable in-app purchase (Pro Unlock). All metadata, price, availability, and the App Review screenshot are complete, and its status is Ready for Review. Rejected first under 2.1 (information needed), then, after I resubmitted, under 2.1(b): the in-app purchase “has not been submitted for review.” Apple’s instruction was to submit the purchase and upload a new binary. What I can’t do Adding the purchase for review creates a stand-alone Draft Submission that says: “Unable to Submit for Review. To submit your items for review, add an app version for the selected platform.” The version is never offered, and Submit stays disabled. The app version is held by the rejected submission, where the only option is Resubmit. That sends the version alone, which is what caused the rejection. The version page doesn’t show an “In-App Purchases and Subscriptions” section, so there’s nowhere to attach the purchase, contrary to what Apple’s help pages describe. I uploaded a new build, attached it to the version, deleted the stale draft, and tried every Add for Review path I could find. The result is the same. Why this isn’t acceptable App Review’s own message tells developers to do something that App Store Connect currently doesn’t allow. Everything Apple needs to see this is on Apple’s side: the account shows a configured purchase, a version in a rejected submission, and a draft that cannot be submitted. The state is visible without any information from me, yet the response so far is a rejection that repeats an instruction I can’t carry out. Each rejection costs developers days. What I’m asking Apple to do Attach the in-app purchase to the existing submission for the version, or Release the version from the rejected submission, so a single new submission can contain both. Acknowledge whether this is a known App Store Connect issue, and when it will be fixed. Other, older threads reporting similar issues and no posted solution include: link text link text link text I’ve also contacted Developer Support and replied in the Resolution Center. Could an Apple staff member look at this thread and my submission (ID ef48c4f6-1ad2-46d8-bb95-46c20bffc82a)? To anyone else with the same problem: please say so, and describe whether you found any workaround that didn’t require recreating your product IDs.

Our first submission has been in "Waiting for Review" for 11 days no status change, no reviewer contact, no reply from Developer Support. App: AMIMA Apple ID: 6823950313 Version: 1.0.0 (build 1) Submission ID: 1dec8fe9-3a94-4ddb-87d8-161791711af7 Submitted: 17 October 2026 Morocco only, free, no in-app purchases Everything on our side is complete: membership paid and active, Free App Agreement active, DSA declaration done, build processed and "Ready to Submit", metadata and privacy complete, demo credentials supplied for a login-gated app. No messages from App Review. We contacted Developer Support on 23 October and have had no reply in five days. The app is the official application of a Moroccan association and is due to be presented to its members at a national congress next week. Apple's published guidance is that most submissions are reviewed within 48 hours; we are at more than five times that with no information. Can anyone from Apple confirm whether this submission is correctly queued? Thank you.

Hello App Review team, Our minorly revised app submission has been stalled for >5 days and like others is stuck on Waiting for Review. One thing that may be related: since the submission, App Store Connect has shown a banner asking the Account Holder to accept the updated Paid Applications Schedule, but in the Business module the Paid Apps row offers only "View Terms" with no Agree button, and there is nothing to accept on developer.apple.com either. I am the Account Holder. If that pending schedule is what is holding the review, we need Apple's help to clear it today, because it cannot be accepted from our side. App name: Girl JuJu Apple ID: 6816548377 Version: 1.0.0 (build 6) Submitted: October 23, 2026 Current status: Waiting for Review This is extremely urgent. Girl JuJu is being showcased at an event on October 30, and we need the app approved and ready to release by end of day October 29. The event was planned around a normal review turnaround from the October 23 submission, and 5 days at Waiting for Review has left us 1 day. The previous build of this version (build 4) was already approved by App Review and is at Pending Developer Release; build 6 is the same app with updated question content and a fix to how the app loads on first open, so nothing about the app's scope or purchases has changed. Google Play has approved the same release. We're ready to provide anything the review team needs right away, including a demo account or additional info, which we can share privately. Could someone confirm whether anything is blocking the submission or needed from our side, and whether an expedited review is possible given the October 30 date? Thank you, Christine Clancy, Girl Juju, Inc. (Team ID HLF8K8QY79)

Hello, Our first release was rejected under Guideline 2.1(b) because subscriptions were unavailable during App Review. We have been unable to reproduce the issue and would appreciate guidance on further diagnostics. Review environment App version: 1.0.0 (9) Device: iPad Air 11-inch (M3) OS: iPadOS 27.0.1 Internet connection: Active, according to the review message The app integrates StoreKit through RevenueCat and offers three auto-renewable subscriptions. We verified that : The Paid Apps Agreement, banking information, and tax forms are active. All three subscriptions and their subscription group are included in the submission. The subscriptions are available in all countries and regions. The submitted build uses the RevenueCat App Store SDK key, rather than a Test Store key. We tested subscription loading 15 times across two networks, including on iPad. Prices loaded successfully, and we completed a sandbox purchase that unlocked Premium. Additional diagnostics on an iPad Air 11-inch (M3) simulator running iPadOS 26.5 returned all three products both through a direct StoreKit Product.products(for:) request and through RevenueCat. No local StoreKit configuration file was attached. We have not reproduced the exact iPadOS 27.0.1 review environment. The simulator runtime is unavailable through our installed Xcode. The rejection message states that subscriptions were unavailable, but does not identify whether product retrieval failed, the subscription options were missing, or a purchase attempt failed. We are asking App Review for those details and a retry. We were wondering: What additional diagnostics would help investigate product availability failures that occur only during App Review? Are there sandbox account or storefront conditions we should test beyond successful product loading and sandbox purchases? Is there a recommended way to collect useful StoreKit error information from a review session when the failure cannot be reproduced locally? Thanks !

Hi, Our submission has been in "Waiting for Review" for 11 days with no status change, and I would like advice on whether to keep waiting or to submit a newer build. Details: App: StarTarot: Your Day, Charted Apple ID: 6807977612 Version / build: 1.2.6 (39) Submission ID: 24f9028e-038f-4d18-9eaf-9a3ca0ccdd70 Submitted: 9 September 2026. It has never moved to "In Review". I also contacted App Review Status through the Contact Us form on 18 September 2026 (Case ID 102967722276) and have not received a reply yet. Background, in case it matters: an earlier submission of this app was rejected under Guideline 4.3(b) as duplicating widely available astrology apps. We did not resubmit the same thing. We reworked how the app presents itself and submitted a new build, because the part that makes it different was not visible from the product page. The app is built around "Today", a daily practice that works as a loop rather than a one-off reading: a digest computed for that specific date from the user's own birth chart (Swiss Ephemeris, NASA/JPL DE440); on some days one small concrete action chosen to fit the day, including the weather and daylight where the user lives; an evening check-in, after which the app asks whether that action happened and adapts what it suggests next; a memory of short facts that the user can review and erase, used only with explicit consent; and an astrologer the user can talk to about timing, a decision or another person. Elsewhere in the app there is astrocartography drawn on a world map, a Human Design bodygraph, recognition of a physical tarot deck photographed with the camera, and eclipse and planet visibility computed for the user's own coordinates. Our 78-card text corpus is published openly under CC BY with a DOI. My questions: Is 11 days without moving to "In Review" expected at the moment, or does it suggest this submission needs attention? We have a further updated build ready (an interactive calendar among other changes). Should we wait for the current submission to be reviewed, or replace the build? We would rather not resubmit repeatedly, since that is discouraged. Thank you.

Our app (Apple ID 1579271306, v1.1.0) was resubmitted Oct 19 after we answered a Guideline 2.1 information request. Expedited review was approved Oct 23, and we opened case 103009324433 on Oct 26. The status hasn’t changed and the demo account hasn’t been signed into. Is there anything else we should do?

Adding my case to this thread. Two apps, both first-time submissions: YAA (delivery app) YAA PRO (courier companion app) Submitted: 14 October 2026 Status: "Waiting for Review" for twelve days, never entered review. On 26 October I cancelled both submissions and resubmitted them, after noticing that my Free Apps agreement only became effective on 19 October — five days after the original submission. My DSA trader status was also incomplete at first and is now active. It is now 28 October and both are still "Waiting for Review", around 50 hours after resubmission. I have an open case with Developer Support, no reply yet. Two questions for the thread: Has anyone confirmed whether cancelling and resubmitting resets your position in the queue? I may have made things worse. Has anyone whose agreement became effective after their submission date seen that cause a delay? Both apps are blocked identically, which makes me think it is not app-specific. Good luck to everyone else waiting.

Hello App Review team, Tankruption (Apple ID 6822420011), iOS version 0.1.277 / build 277, has remained Waiting for Review since our October 21, 2026 resubmission (11:48 PM as displayed in App Store Connect). After resubmission we identified a startup issue and uploaded corrected version 0.1.286 / build 286, which has since been approved for TestFlight. We disclosed the issue and candidate build in App Review Notes and a production-thread message on October 25. Build 277 remains formally attached to the production submission; we understand that naming a build in a note does not replace that association. We opened Developer Support case 103011603232 on October 28 to ask whether App Review can coordinate the corrected build while retaining the existing queue position, or whether we must withdraw and formally resubmit. We have kept the current submission in place while requesting guidance. Could an Apple representative confirm the appropriate process and whether anything else is needed from us? We can provide further details privately through the support case or App Store Connect. Thank you.

Hello App Review team, My first app is waiting for review, and I'd like to make it as quick and easy for you as possible. App: Coinarium - coin collection organizer for iPhone Apple ID: 6823220807 Version: 1.0 (build 7) Submission ID: 3520cdd4-5651-4f65-9310-136b38d42949 Submitted: October 15, 2026 Status: Waiting for Review On October 16 the review returned Guideline 2.1 "Information Needed - New App Submission". The same day I replied with everything requested: a screen recording from a physical iPhone covering the whole app, its purpose and audience, step-by-step instructions, external services, regional differences and third-party content. The same information is in the App Review Notes, and the build was resubmitted. Why it should be a quick review: Small app: three tabs and fewer than ten main screens. Nothing to set up: no account, no login, no demo credentials, no in-app purchases, no ads, no analytics. No user-generated content, no social features, age rating 4+. All data stays on the device. The only network request is an optional Google Lens photo search, made only when the user taps a button, in a web view limited to Google pages. Privacy policy, support page, screenshots and metadata are complete in English, Polish and Russian. 3-minute review path: Collection tab, "+": pick a country, denomination and year, take a photo, save. Tap "+" again with the same coin: the app shows "Already Have It" with the existing coin. Wishlist tab: add a wanted coin and share the list. Settings: create a backup to Files. I understand how many submissions you handle every day and I'm not asking to skip the queue. I only want to make sure my reply reached the reviewer and that nothing is missing on my side. If anything else is needed, I'll respond within hours. Thank you for your time and for keeping the App Store a great place for users and developers. Best regards, Andrey

Hi all, I'm looking for guidance on getting my app back on sale. I've done everything I know to do and I'm not sure what step I'm missing. Details below. Timeline: Aug 16: The app was removed from sale through App Store Notices (ref APP265997). Sept: I renamed the app with a new name, icon, and listing, which was the agreed resolution. Oct 2: Apple lifted the submission hold. Oct 5: The other party confirmed to App Store Notices that the matter is closed and the app can be restored. Oct 7: Version 1.0.4 was approved. App Store Connect shows it as "Ready for Distribution," but the version page also shows a banner: "This app was removed from sale from the App Store." The product page returns "can't be found." I've accepted all current agreements. Oct 20: I submitted 1.0.5 (Manual release). It has been in "Waiting for Review" for 8 days and hasn't moved to In Review. Oct 23: I followed up with App Store Notices and have not heard back yet. My questions: Once an App Store Notices matter is closed, is there a separate step to restore the app to sale, or does App Store Notices lift the removal on their end? Could the removal be why 1.0.5 hasn't entered review after 8 days? Is there a better contact or channel for this than the App Store Notices thread? Any guidance from Apple staff or anyone who has been through this would be a huge help. Existing users can't get the latest fixes, and new users can't find the app at all. Thank you.